ci(release): correct channel semantics for semver prereleases - #1303
Merged
Conversation
A version containing a prerelease suffix (v0.9.1-rc.1) now publishes as an RC on every channel instead of masquerading as stable: - GitHub release is created with prerelease: true (never marked Latest) - npm publishes under the `next` dist-tag, so plain `npm install` keeps serving the last stable; testers opt in with codebase-memory-mcp@next - the MCP Registry sync is skipped (the registry has no channel concept) - PyPI needs no change: PEP 440 already treats rc versions as pre-releases that pip only installs with --pre Stable releases (no dash) are byte-identical in behavior. Signed-off-by: Martin Vogel <martin.vogel.tech@gmail.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
A version containing a prerelease suffix (
v0.9.1-rc.1) now publishes as an RC on every channel instead of masquerading as stable:prerelease: true(never marked Latest)nextdist-tag — plainnpm installkeeps serving the last stable; testers opt in viacodebase-memory-mcp@nextrcversions as pre-releases pip only installs with--preStable releases (no dash in the version) are byte-identical in behavior. Workflows-only change; product code untouched relative to the green dry-run SHA
d587dea(run 30244476878). Unblocks thev0.9.1-rc.1dispatch.